>mvn -Pdistro versions:set -DnewVersion=2.1.0 >mvn -Pdistro versions:commit
Set the version for the target release
>mvn -Pdistro versions:set -DnewVersion=2.1.0 >mvn -Pdistro versions:commit
Before you can start, make sure that your public SSH key is registered for use with osgi@filemgmt.jboss.org. This key will be used instead of a password. You can do this by emailing the public key to help@jboss.org.
Obtain a snapshot of the API docs either by building http://github.com/jbosgi/jbosgi/tree/master/distribution or by downloading them from a successful hudson build. The API docs are built at distribution/javadoc/target/apidocs.
Then copy them to a specific location for this release in the documentation directory using scp:
cd distribution/javadoc/target mkdir jboss-osgi-2.1.0; mv apidocs jboss-osgi-2.1.0 scp -r jboss-osgi-2.1.0 osgi@filemgmt.jboss.org:docs_htdocs/osgi/jboss-osgi-2.1.0
Then update the link from the API docs to the latest versions:
$ sftp osgi@filemgmt.jboss.org:docs_htdocs/osgi Connecting to filemgmt.jboss.org... Changing to: /docs_htdocs/osgi sftp> rm apidocs sftp> ln -s jboss-osgi-2.1.0/apidocs apidocs
Check that you see the desired results at:
Copy the release notes from the JIRA Roadmap to ChangeLog.html
Extract the relevant changes to ReleaseNotes.html
Add the user and developer guides to the distribution dir
When you've done all of the above you can tag the release and deploy it to Nexus
>git tag -a 2.1.0 -m "Release 2.1.0" >git push upstream 2.1.0 >git checkout 2.1.0 >mvn -Pdistro clean deploy
Close and promote the release in the Nexus Repository.
Follow Deploying a Release on how to do this.
Upload the installer, the changelog and the release notes.
Check the result at the JBossOSGi download area
Create a news wiki page and link to it from the main wiki page
Blog about the release on JBossOSGi Diary (http://jbossosgi.blogspot.com)
Advertise the release on mailing lists (i.e. jboss-development@lists.jboss.org, thecore@jboss.org)